PI Planning Template
Bring your team toward one vision and decide what stories to develop with the PI Planning Template. Manage your team's backlog, increase productivity, and build the foundation for a successful PI Planning event.
Trusted by 65M+ users and leading companies
About the PI Planning Template
Many product teams and agile facilitators use PI Planning to align and bring teams towards one shared vision. PI Planning is supposed to happen in person, but since the rise of hybrid work, many teams run it remotely. Miro’s PI Planning Template helps you get an excellent overview of your PI Planning event, with step-by-step frames that will guide you through the whole process.
Keep reading to know more about how to use the PI Planning Template.
What is PI planning?
PI planning or “program increment planning” is a method for strategizing toward a shared vision among teams. In a PI planning event, teams, stakeholders, and project owners are assembled to review a program backlog and determine what direction the business will take next. Typically, organizations carry out PI planning every 8 to 12 weeks.
Benefits of PI planning
PI planning can be useful in a number of ways, and teams in various industries apply the PI methods to boost efficiency and productivity.
Establish face-to-face communication
One advantage of PI planning is that it enables all the various stakeholders and teams on a project to meet face-to-face and talk about the overall mission and goals. This is the crucial first step towards aligning all the different parties towards the same mission and goals.
Boost productivity
PI planning fosters cross-team and cross-Agile Release Team (ART) collaboration and establishes a clear backlog and schedule for when tasks should be completed. With teams syncing and communicating in the right way and focused on their own goals, overall team productivity improves.
Align team goals
One of the main goals of the PI planning process is to set clear goals and ensure that all stakeholders and team members are working towards that goal. Making sure that everyone understands and shares the same goal is the foundation of a unified team effort.
When to use PI planning
PI planning is part of the Scaled Agile Framework (SAFe), which is designed to help developers overcome the challenge of coordinating across teams, processes, and programs. In the SAFe model, teams are assembled into Agile Release Trains (ARTs), each of which works on a specific part of a broader goal.
To engage in PI planning, the Agile Release trains are brought together every 8 to 12 weeks. A PI planning event is an opportunity to step back and ensure everyone is still working toward the same business goals and is satisfied with the overall vision.
Create your PI Planning board
You can easily organize a PI Planning event remotely or in-person with Miro. Our PI Planning Template is divided into four parts:
Agenda
Program Board
ROAM Board
Teams Board
Read below to see how to use each part of the PI Planning Template:
PI Planning Agenda
Have a dedicated space to share the PI Planning schedule, where every participant will know what to expect and when. This will include all the PI Planning stages. Add a Program Backlog so you and your team know what still needs to be worked on.
Program Board (SAFe)
Here is where you and your team add milestones and iterations and how they correlate. Color-code tasks and connect them with lines and arrows to indicate flows and interdependencies. On the Program Board, you will overview features, dependencies, and milestones.
ROAM Board
A ROAM Board is where you and your team can see the program’s risks. That’s the moment to identify obstacles to achieving goals and decide how to proceed. Use the voting feature to perform the confidence vote.
Teams Board
Each team will have precise future iterations, tasks, and objectives moving forward. What’s on this frame needs to be included in the roadmap.
General considerations when running a PI Planning session:
Bring everyone together
Make sure all stakeholders, teammates, and project owners are present for the first all-hands planning session. For remote PI planning, you might choose to use video conferencing tools, which are widely used now.
Clarify team goals
Now, the team comes together to articulate the vision for the product or solution. Answer these questions: How are you filling customer needs? How have market changes impacted your ability to do so?
Draft a plan
Bring all these components together in a project management document for management and teams to review.
Tip: you can easily add Jira cards to your PI planning board to organize Jira issues and mark dependencies.
How do you do PI Planning?
A PI Planning event has a duration of 2 days, and it can be done remotely or in person. To run a successful PI Planning session, make sure that at the end of it you and your team come out with two things: committed PI Objectives and a Program Board where you will see the next milestones and delivery dates.
What are the PI planning stages?
The PI Planning event is divided into two days. On the first day, present your business context, draft a plan and manage and review blockers or constraints. The second day is meant to review your plan, evaluate program risks, perform the confidence vote and plan the rework and next steps.
Get started with this template right now.
Service Blueprint Template
Works best for:
Desk Research, Operations, Market Research
The Service Blueprint template is a visual tool for designing and optimizing service experiences. It provides a structured framework for mapping customer journeys, identifying touchpoints, and aligning internal processes. This template enables teams to visualize the entire service ecosystem, uncover pain points, and innovate solutions to enhance customer satisfaction. By promoting customer-centricity and collaboration, the Service Blueprint empowers organizations to deliver exceptional service experiences and drive sustainable growth.
3x3 Prioritization Method Template
Works best for:
Operations, Prioritization, Strategic Planning
It’s all about assessing a task or idea, and quickly deciding the effort it will take and the potential impact it will have—ranked low, medium, or high. That’s what the 3x3 prioritization method does: Help teams prioritize and identify quick wins, big projects, filler tasks, or time-wasters. With nine bucket areas, it offers slightly greater detail than the 2x2 Prioritization Matrix (or Lean Prioritization Method). It’s easy to make your own 3x3 prioritization matrix—then use it to determine what activities or ideas to focus on with your valuable resources.
Product Backlog Template
Works best for:
Agile Methodology, Kanban Boards, Product Management
Development teams are often juggling many products at once. A product backlog is a project management tool that helps teams keep track of projects in flight as they build and iterate, so you can store everyone's ideas, plan epics, and prioritize tasks. The highest-priority tasks are at the top of the product backlog, so your team knows what to work on first. Product backlogs make it easier for teams to plan and allocate resources, but it also provides a single source of truth for everyone to know what development teams are working on.
Scope of Work Template
Works best for:
Project management, Planning
The Scope of Work Template from Miro brings structure, clarity, and efficiency to project planning. It's more than just a template—it's an adaptable and dynamic platform that adapts to your unique project needs. Join thousands of satisfied users and make the Scope of Work Template a part of your project management toolkit.
PRD Template
Works best for:
Product Development, Product , Management
The PRD Template by Miro is a blueprint designed to streamline the product development process. Acting as a central hub for all essential details, this template ensures team alignment by laying out clear project objectives, use cases, and design specifics. The primary benefit? Seamless communication and clarity, reducing the likelihood of missteps and fostering a smooth transition from idea conception to product launch.
Status Report Template
Works best for:
Project Management, Documentation, Strategic Planning
A status report provides a snapshot of how something is going at a given time. You can provide a status report for a project, a team, or a situation, as long as it emphasizes and maps out a project’s chain of events. If you’re a project manager, you can use this report to keep historical records of project timelines. Ideally, any project stakeholder should be able to look at a status report and answer the question, “Where are we, and how did we get here?” Use this template as a starting point to summarize how something is progressing against a projected plan or outcome.